Problem

When a sync config has noWatch: true, SSH server injection never starts. The SSH section in devspace.yaml is completely ignored when any sync entry has noWatch: true.

Root Cause

The dev mode starts services in sequence: sync → port forwarding → SSH. SSH only starts after sync initialization completes (<-syncDone).

When noWatch: true:

1. StartSync creates a cancelable context for that sync entry
2. The sync goroutine starts, completes initial sync, and returns
3. defer cancel() fires, cancelling the context
4. Meanwhile, startWithWait() had registered a RestartOnError goroutine via parent.Go() that listens on ctx.Context().Done()
5. The context cancellation triggers this handler, which calls syncStop() → parent.Kill(nil)
6. The parent tomb enters a dying state
7. SSH (which starts after <-syncDone) either cannot start or is immediately terminated because the tomb is dying

Fix

Set RestartOnError to false when NoWatch is true. A one-shot sync has no need for restart-on-error handling since it completes after initial sync. This prevents the restart handler goroutine from being registered, which in turn prevents it from killing the parent tomb when the cancelled context fires.

Change

In pkg/devspace/services/sync/sync.go, startSync():

// Before:
RestartOnError: true,

// After:
RestartOnError: !syncConfig.NoWatch,

Fixes #3005